CVE-2023-53137
ext4: Fix possible corruption when moving a directory
Description
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
INFO
Published Date :
May 2, 2025, 4:15 p.m.
Last Modified :
Sept. 5, 2025, 8:15 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Solution
- Update the Linux kernel to a patched version.
- Ensure directory modifications are properly locked.
- Test the system for stability after the update.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2023-53137 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2023-53137 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Rejected by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Sep. 05, 2025
Action Type Old Value New Value -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Sep. 05, 2025
Action Type Old Value New Value Changed Description In the Linux kernel, the following vulnerability has been resolved: ext4: Fix possible corruption when moving a directory When we are renaming a directory to a different directory, we need to update '..' entry in the moved directory. However nothing prevents moved directory from being modified and even converted from the inline format to the normal format. When such race happens the rename code gets confused and we crash. Fix the problem by locking the moved directory. Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. Removed Reference kernel.org: https://git.kernel.org/stable/c/0813299c586b175d7edb25f56412c54b812d0379 Removed Reference kernel.org: https://git.kernel.org/stable/c/0c440f14558bfacd22c6935ae1fd4b2a09e96b5d Removed Reference kernel.org: https://git.kernel.org/stable/c/291cd19d107e197306869cb3237c1bba62d13182 Removed Reference kernel.org: https://git.kernel.org/stable/c/8dac5a63cf79707b547ea3d425fead5f4482198f Removed Reference kernel.org: https://git.kernel.org/stable/c/b0bb13612292ca90fa4c2a7e425375649bc50d3e Removed Reference kernel.org: https://git.kernel.org/stable/c/c50fc503ee1b97f12c98e26afc39fdaebebcf04f -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 02, 2025
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: ext4: Fix possible corruption when moving a directory When we are renaming a directory to a different directory, we need to update '..' entry in the moved directory. However nothing prevents moved directory from being modified and even converted from the inline format to the normal format. When such race happens the rename code gets confused and we crash. Fix the problem by locking the moved directory. Added Reference https://git.kernel.org/stable/c/0813299c586b175d7edb25f56412c54b812d0379 Added Reference https://git.kernel.org/stable/c/0c440f14558bfacd22c6935ae1fd4b2a09e96b5d Added Reference https://git.kernel.org/stable/c/291cd19d107e197306869cb3237c1bba62d13182 Added Reference https://git.kernel.org/stable/c/8dac5a63cf79707b547ea3d425fead5f4482198f Added Reference https://git.kernel.org/stable/c/b0bb13612292ca90fa4c2a7e425375649bc50d3e Added Reference https://git.kernel.org/stable/c/c50fc503ee1b97f12c98e26afc39fdaebebcf04f